I don't have any issues with screensavers, however, I am getting the same XIB exception in my app when compiled with Xcode 26 and running in macOS 15. The issue in my case is related to NSOutlineView, just having it in a storyboard is enough to trigger that. Submitted FB19632073

I have created a sample project and submitted a bug report FB18771900. Basically any UIToolbar in a storyboard compiled with iOS 26 SDK will crash in iOS 18.

I also have exactly the same problem.

I can confirm that there is something wrong with how Icon Composer icons are compiled in Xcode beta 3. For instance, I am no longer able to upload my app to the App Store Connect (for TestFlight), I am getting a validation error from the App Store Connect about a missing icon for older versions of iOS. Removing the glass icon fixes the issue. FB18760234

[quote='848223022, DTS Engineer, /thread/791882?answerId=848223022#848223022'] I recommend that you start a new thread about this in the Privacy & Security > Sign in with Apple topic area. [/quote] Thanks! I tried posting a thread there, unfortunately it looks like it is not possible to create a new thread for "Sign in with Apple". I always get "This post contains sensitive language. Please revise it in order to continue". Created FB18737304.

Many thanks for clarifying the migration process, Quinn. One more question - my app currently supports "Sign in with Apple" and it is enabled as the "Primary App ID" with its non-Team ID prefix. The fact that the "Sign in with Apple" settings page is using App IDs and not bundle IDs is a bit concerning since the App ID will change after migration. Do you know by any chance how "Sign in with Apple" is implemented under the hood, is it directly tied to the App ID or it is working with Bundle IDs? I don't want to reset my current "Sign in with Apple" users :)

Hi Quinn, Many thanks for your detailed reply, I really appreciate it. What would be the correct way to proceed with the migration to the Team ID as the App ID prefix? Do I just delete the app identifier in the Developer portal, then create a new one with the same bundle ID but the correct (Team ID) App ID prefix? Also, am I correct assuming that any changes that I make this way don't affect the App Store version of the app until a new update is actually released on the App Store?

It is broken. Submitted FB12555541 one month ago, no response yet.

Fixed in Xcode 15 beta 3.

Ok, it looks like either Xcode 15 or the App Store Connect that is mistakenly marking AVFoundation framework as private. Hence the bug. After stripping AVFoundation from my project, I was able to avoid this error. Good luck if your 3rd party library is using it though. What is interesting is that if you check the main header for AVFoundation you will see similar files that are getting imported by the framework and then marked as private: #if __has_include(<AVFoundation/AVFCore.h>) #import <AVFoundation/AVFCore.h> #else #import <AVFCore/AVFCore.h> #endif #if __has_include(<AVFoundation/AVFAudio.h>) #import <AVFoundation/AVFAudio.h> #endif #if __has_include(<AVFoundation/AVFCapture.h>) #import <AVFoundation/AVFCapture.h> #else #import <AVFCapture/AVFCapture.h> #endif Submitted FB12425841

Same problem. Looks like a bug in the App Store Connect.

Same issue in Xcode beta 4 :(

Same problem here. Looks like App Intents are a bit rough in beta 1.

Fixed in beta 5.

Please don't forget to create a new feedback. Apple needs to prioritize this bug.